<?xml version="1.0" encoding="utf-8"?>
<!--
                                                                                     
 h       t     t                ::       /     /                     t             / 
 h       t     t                ::      //    //                     t            // 
 h     ttttt ttttt ppppp sssss         //    //  y   y       sssss ttttt         //  
 hhhh    t     t   p   p s            //    //   y   y       s       t          //   
 h  hh   t     t   ppppp sssss       //    //    yyyyy       sssss   t         //    
 h   h   t     t   p         s  ::   /     /         y  ..       s   t    ..   /     
 h   h   t     t   p     sssss  ::   /     /     yyyyy  ..   sssss   t    ..   /     
                                                                                     
	<https://y.st./>
	Copyright © 2016 Alex Yst <mailto:copyright@y.st>

	This program is free software: you can redistribute it and/or modify
	it under the terms of the GNU General Public License as published by
	the Free Software Foundation, either version 3 of the License, or
	(at your option) any later version.

	This program is distributed in the hope that it will be useful,
	but WITHOUT ANY WARRANTY; without even the implied warranty of
	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
	GNU General Public License for more details.

	You should have received a copy of the GNU General Public License
	along with this program. If not, see <https://www.gnu.org./licenses/>.
-->
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<base href="https://y.st./en/weblog/2016/08-August/11.xhtml"/>
		<title>Basic computer concepts &lt;https://y.st./en/weblog/2016/08-August/11.xhtml&gt;</title>
		<link rel="icon" type="image/png" href="/link/CC_BY-SA_4.0/y.st./icon.png"/>
		<link rel="stylesheet" type="text/css" href="/link/main.css"/>
		<script type="text/javascript" src="/script/javascript.js"/>
		<meta name="viewport" content="width=device-width"/>
	</head>
	<body>
<nav>
	<p>
		<a href="/en/coursework/">Coursework</a> |
		<a href="/en/take-down/">Take-down requests</a> |
		<a href="/en/">Home</a> |
		<a href="/en/a/about.xhtml">About</a> |
		<a href="/en/a/contact.xhtml">Contact</a> |
		<a href="/a/canary.txt">Canary</a> |
		<a href="/en/URI_research/"><abbr title="Uniform Resource Identifier">URI</abbr> research</a> |
		<a href="/en/opinion/">Opinions</a> |
		<a href="/en/law/">Law</a> |
		<a href="/en/recipe/">Recipes</a> |
		<a href="/en/a/links.xhtml">Links</a> |
		<a href="/en/weblog/2016/08-August/11.xhtml.asc">{this page}.asc</a>
	</p>
	<hr/>
	<p>
		Weblog index:
		<a href="/en/weblog/memories">Memories</a> |
		<a href="/en/weblog/"><abbr title="American Standard Code for Information Interchange">ASCII</abbr> calendars</a> |
		<a href="/en/weblog/index_ol_ascending.xhtml">Ascending list</a> |
		<a href="/en/weblog/index_ol_descending.xhtml">Descending list</a>
	</p>
	<hr/>
	<p>
		Jump to entry:
		<a href="/en/weblog/2015/03-March/07.xhtml">&lt;&lt;First</a>
		<a rel="prev" href="/en/weblog/2016/08-August/10.xhtml">&lt;Previous</a>
		<a rel="next" href="/en/weblog/2016/08-August/12.xhtml">Next&gt;</a>
		<a href="/en/weblog/latest.xhtml">Latest&gt;&gt;</a>
			</p>
			<hr/>
</nav>
		<header>
			<h1>Basic computer concepts</h1>
			<p>Day 00523: <time>Thursday, 2016 August 11</time></p>
		</header>
<p>
	I&apos;ve been routing my mother&apos;s Internet traffic on their desktop machine through <abbr title="The Onion Router">Tor</abbr> on my mobile.
	The fact is, if I didn&apos;t route this traffic through my mobile, my mother&apos;s machine wouldn&apos;t have any Internet connection at all, as we&apos;re currently living without home Internet service.
	If my connection is being used, I&apos;m absolutely not going to expose my <abbr title="Internet Protocol">IP</abbr> address for it.
	It&apos;s not my job to do that.
	Anyway, my mother decided to pay a visit to craigslist.
	The first problem here is that craigslist maliciously discriminates against <abbr title="The Onion Router">Tor</abbr> users, so they were sending nothing but <abbr title="Hypertext Transfer Protocol">HTTP</abbr> 403 Forbidden response codes and error pages.
	The second issue is that my mother uses Internet Explorer.
	Internet Explorer has this fun little feature that causes it to avoid displaying error pages.
	Instead, it displays a &quot;possible causes&quot; message.
	Instead of allowing the user to hear directly from the server what the issue is, Internet Explorer wants to interject with mere <strong>*guesses*</strong>! In this case, Internet Explorer said that the most likely cause is that one must log in before viewing pages on that website.
	I swear, Internet Explorer is moronic.
	There was no value in explaining what I believe the cause of the problem was though, as it would be interpreted the wrong way.
	My mother would blame the proxy, but it&apos;s not the proxy&apos;s fault.
	The proxy isn&apos;t blocking the page.
	No, what my mother will likely always fail to grasp is that the problem is those that maliciously discriminate against proxies.
	In any case, as no real information on the issue was actually available, I didn&apos;t make such speculations out loud.
	Instead, I worked with the information provided.
	I said that clearly, craigslist was having issues at the moment, then convinced my mother to try a different website.
	I&apos;m surprised that they were willing to try something else, given their usual attitude, but they indeed did take their business elsewhere.
</p>
<p>
	Later that day, my mother wanted to go through their photographs and print out a couple hundred of them.
	They had me back the photographs up to their desktop machine earlier in the day, but then for some reason felt the need to upload them directly from the mobile to some Google service.
	Mother said that they were going to try to put the couple hundred that the wanted on a <abbr title="digital versatile disc">DVD</abbr>, so I said that I could burn photographs that are on the computer, not on Google, to the <abbr title="digital versatile disc">DVD</abbr> if they wanted help.
	They said that that would be great, but wanted to finish the Google upload that they were in the middle of first because if that was interrupted and the way I wanted to do it didn&apos;t work as expected (there&apos;s no reason that it wouldn&apos;t have), they&apos;d have to restart the upload to do it that way.
	I left, and when they called me back over, they&apos;d sorted the photographs that they wanted to keep <strong>*on Google*</strong> and expected me to save the files to the <abbr title="digital versatile disc">DVD</abbr>! There was no indication of how to download the photographs back to the desktop machine in the Google interface, so I did the only thing that I could: I attempted to find each photograph in my mother&apos;s offline collection that matched what was displayed in Google.
	My mother came over to check and see how I was doing and what was taking so long, so I explained the situation.
	I had never said that I could burn images to a <abbr title="digital versatile disc">DVD</abbr> from Google, only that I could do it from local files! I could of course save each thumbnail image, and burn those, but there would be a severe drop in image quality.
	My mother didn&apos;t seem to understand the difference between a file on a distant server that I don&apos;t have access to and a file on the local machine.
	They said that if I could only copy the ones from the local machine, I should just to that, so I explained that that is what I was doing; I was having to hunt down each photograph by hand from the local collection.
	So far I&apos;d located three and failed to find two.
	Uploading files to Google then expecting to somehow burn them to a <abbr title="digital versatile disc">DVD</abbr> had been a stupid plan, though I didn&apos;t say that part out loud.
	I think that because my mother could see all the thumbnails on the webpage, they thought that the actual photographs were within reach and could be saved directly to a <abbr title="digital versatile disc">DVD</abbr> or anything else.
</p>
<p>
	From there, my mother took over and started trying to make Google give them the photographs.
	I didn&apos;t think that it was necessarily possible, but the two of us worked together and covered each other&apos;s weaknesses.
	I couldn&apos;t fiddle with the account, as it wasn&apos;t my account and if I break anything, it&apos;d be my fault.
	I couldn&apos;t do anything that would make permanent changes.
	My mother on the other hand couldn&apos;t tell the difference between the interface provided by the webpage and the menu of the Web browser itself.
	They didn&apos;t get that they two had different contexts and were limited in different ways in what they could do.
	For that matter, they couldn&apos;t distinguish these contexts from the context of local applications.
	First, they wanted to use the &quot;save&quot; option in the Web browser menu to save the album in photograph form (as opposed to webpage form) to the local machine.
	Then they wanted to use the &quot;save&quot; option in the Web interface to safe the album to the local machine (as opposed to save the changes made online to the serve).
	I was able to guide my mother around those pitfalls while they navigated the website looking for a solution that I thought might not even exist, until I spotted the &quot;download&quot; option which was what we clearly needed.
</p>
<p>
	In retrospect, it seems rather obvious that Google would offer <strong>*some*</strong> way to download the photographs that one uploads, though they did make that option difficult to find and an &quot;album&quot; had to be created from the subset of photographs that my mother wanted first, while somehow the set that my mother had set up before was not considered to be an album.
	Mostly, I think that I didn&apos;t think that it was possible because I was still flabbergasted by the inefficiency of uploading files for sorting that you actually want to be stored locally.
</p>
		<hr/>
		<p>
			Copyright © 2016 Alex Yst;
			You may modify and/or redistribute this document under the terms of the <a rel="license" href="/license/gpl-3.0-standalone.xhtml"><abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License version Three or later">GPLv3+</abbr></a>.
			If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
			My address is in the source comments near the top of this document.
			This license also applies to embedded content such as images.
			For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
		</p>
		<p>
			<abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
			This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F08-August%2F11.xhtml"><abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.2</a> specification and uses style sheets that conform to the <a href="http://jigsaw.w3.org./css-validator/validator?uri=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F08-August%2F11.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
		</p>
	</body>
</html>

